Add daemon.json with overlay2 to fix container startup issue #351
Conversation
polmoorx
force-pushed
the
fix-docker-startup-overlay2
branch
2 times, most recently
from
6b58436 to
5110a47
Compare
polmoorx
force-pushed
the
fix-docker-startup-overlay2
branch
4 times, most recently
from
ee1ab22 to
34d3f78
Compare
polmoorx
force-pushed
the
fix-docker-startup-overlay2
branch
3 times, most recently
from
4a3f4e2 to
686f4fa
Compare
polmoorx
force-pushed
the
fix-docker-startup-overlay2
branch
5 times, most recently
from
a2838e3 to
f720386
Compare
polmoorx
force-pushed
the
fix-docker-startup-overlay2
branch
from
f720386 to
e876a84
Compare
polmoorx
force-pushed
the
fix-docker-startup-overlay2
branch
2 times, most recently
from
c4934ed to
46d9f21
Compare
SPECS/moby-engine/moby-engine.spec
Outdated
| mkdir -p %{buildroot}/opt/docker-data | ||
| chmod 0700 %{buildroot}/opt/docker-data |
There was a problem hiding this comment.
Redundant to line 118-119, where similar mkdir -p /opt/docker-data and chmod 0700 also added there.
There was a problem hiding this comment.
Thank you for the comment. I have removed the redundant mkdir -p /opt/docker-data and chmod 0700 /opt/docker-data from the %install section, keeping only the creation and permission commands in the %post script.
This is because:
-
The %install section runs during package build time, preparing the package filesystem (buildroot).
-
The %post section runs during package installation on the live system, which is the correct place to ensure /opt/docker-data exists with proper permissions on the target device.
|
Before switching |
polmoorx
force-pushed
the
fix-docker-startup-overlay2
branch
2 times, most recently
from
9022047 to
5319537
Compare
We did try adding /var/lib/docker to PERSISTENT_BIND_PATHS before changing the data-root to /opt/docker-data. But because on EMT OS /var is often temporary (tmpfs) early in boot, Docker’s data under /var/lib/docker wasn’t actually persistent, so the overlayfs errors continued. Changing Docker’s data-root to /opt/docker-data and ensuring it is persistent and created at runtime fixed the problem. |
Added a daemon.json file to set "overlay2" as the storage driver and moved Docker’s data directory to /opt/docker-data. This change makes sure Docker starts properly on EMT OS. Also updated the spec file to install this config and copy any existing Docker data to the new location. Signed-off-by: Polmoorx Shiva Kumar <[email protected]>
polmoorx
force-pushed
the
fix-docker-startup-overlay2
branch
from
5319537 to
00d09b3
Compare
2 participants
Merge Checklist
All boxes should be checked before merging the PR
Description
On EMT OS, when we tried to start Docker, it failed because the default overlay2 storage driver requires a writable, overlay-compatible filesystem, but /var/lib/docker resides under /var, which on EMT OS can be mounted as read-only or which isn’t compatible with overlay operations. This prevented Docker from launching. To fix this, we configured Docker to store its data in /opt/docker-data, a persistent and writable location that supports overlay2, by adding a daemon.json file and updating the RPM spec to create the required directories, install the configuration, and safely migrate any existing data from /var/lib/docker using rsync. With this change, Docker now starts and runs reliably on both RT and non-RT EMT OS, using a stable and compatible storage location.
Any Newly Introduced Dependencies
No
How Has This Been Tested?
Tested manually.